/ 
perl-5.43.4
River stage five • 12010 direct dependents • 33600 total dependents
⭐ Starred 2013 GitHub stars
/ perldelta

NAME

perldelta - what is new for perl v5.43.4

DESCRIPTION

This document describes differences between the 5.43.3 release and the 5.43.4 release.

If you are upgrading from an earlier release such as 5.43.2, first read perl5433delta, which describes differences between 5.43.2 and 5.43.3.

Modules and Pragmata

Updated Modules and Pragmata

  • attributes has been upgraded from version 0.36 to 0.37.

  • B::Deparse has been upgraded from version 1.87 to 1.88.

  • feature has been upgraded from version 1.99 to 2.00. Split POD and code and add __END__. Avoids I/O and parsing 22KB of POD in use feature;.

  • Module::CoreList has been upgraded from version 5.20250923 to 5.20251022.

  • SelectSaver has been upgraded from version 1.02 to 1.03.

  • Time::Piece has been upgraded from version 1.3701 to 1.38.

  • XS::APItest has been upgraded from version 1.46 to 1.47.

Platform Support

Platform-Specific Notes

AIX

Thread-safe locale handling has been turned off on all releases due to apparent bugs in the underlying operating system support.

Selected Bug Fixes

  • The -CA flag (or equivalently, the PERL_UNICODE=A environment setting) tells perl to treat command-line arguments as UTF-8 strings. (See perlrun for details.) However, this did not extend to the global variables implicitly created by the -s option:

    $ perl -CA -s -e 'printf "%vx\n", $_ for $foo, $ARGV[0]' -- -foo=é é
c3.a9
e9

    Here $foo would end up containing the two-byte UTF-8 representation of "LATIN SMALL LETTER E WITH ACUTE", but $ARGV[0] would contain a single codepoint corresponding to U+00E9.

    This has been fixed: If -CA is in effect, options parsed by -s are treated as UTF-8, too. In the example above, $foo and $ARGV[0] now both contain chr(0xE9). [GH #23377]

  • We have long claimed to support identifiers up to about 255 characters long. However this was actually true only for identifiers that consisted of only ASCII characters. The real upper limit was as few as 64 characters for identifiers written in other languages, for example, Chinese or Osage. Now an identifier in any language may contain at least 255 characters.

  • Fixed parsing of array names starting with a digit in double-quotish context under use utf8;.

Acknowledgements

Perl 5.43.4 represents approximately 4 weeks of development since Perl 5.43.3 and contains approximately 18,000 lines of changes across 170 files from 21 authors.

Excluding auto-generated files, documentation and release tools, there were approximately 7,500 lines of changes to 81 .pm, .t, .c and .h files.

Perl continues to flourish into its fourth decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.43.4:

Branislav Zahradník, Daniel Dragan, Elvin Aslanov, Eric Herman, Eugen Konkov, James E Keenan, James Raspass, Karl Williamson, Lukas Mai, Masahiro Iuchi, Paul Evans, Philippe Bruhat (BooK), Ricardo Signes, Richard Leach, Samuel Smith, Sevan Janiyan, Sisyphus, Stan Ulbrych, Thibault Duponchelle, Tom Wyant, Tony Cook.

The list above is almost certainly incomplete as it is automatically generated from version control history. In particular, it does not include the names of the (very much appreciated) contributors who reported issues to the Perl bug tracker.

Many of the changes included in this version originated in the CPAN modules included in Perl's core. We're grateful to the entire CPAN community for helping Perl to flourish.

For a more complete list of all of Perl's historical contributors, please see the AUTHORS file in the Perl source distribution.

Reporting Bugs

If you find what you think is a bug, you might check the perl bug database at https://github.com/Perl/perl5/issues. There may also be information at https://www.perl.org/, the Perl Home Page.

If you believe you have an unreported bug, please open an issue at https://github.com/Perl/perl5/issues. Be sure to trim your bug down to a tiny but sufficient test case.

If the bug you are reporting has security implications which make it inappropriate to send to a public issue tracker, then see "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to report the issue.

Give Thanks

If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by running the perlthanks program:

perlthanks

This will send an email to the Perl 5 Porters list with your show of thanks.

SEE ALSO

The Changes file for an explanation of how to view exhaustive details on what changed.

The INSTALL file for how to build Perl.

The README file for general stuff.

The Artistic and Copying files for copyright information.